fix(memory-ingest): stop dropping capture_origin at ingest (issue #368) - #410

benchmarks/lib/bench_db.py hard-imports PgMemoryStore (-> psycopg) at
module level (established convention, tests_py/benchmarks/
test_lib_init_no_psycopg.py). This test file imported it unconditionally,
which broke collection on the SQLite-only CI lane
("ModuleNotFoundError: No module named 'psycopg'").

Fix: pytest.importorskip("psycopg", ...) before the benchmarks.lib.bench_db
import, matching the pattern already used by
tests_py/integration/test_recall_trust_ranking.py. Verified locally by
poisoning sys.modules for psycopg/psycopg_pool/pgvector — the suite now
skips cleanly instead of erroring, and still passes normally with psycopg
present.

Co-Authored-By: Claude <noreply@anthropic.com>

2026-08-10 incident: a 5-cell trust-factor sweep ran while three other
agents' full pytest suites were active on the same 10-core machine (load
average ~11-14). Cell W=1.0 crashed on a native fatal error (rc=120,
truncated CPython fatal-error signature) -- a visible failure. But a
cell that merely FINISHED under the same contention (saturated
connection pool, cold cache, GC pressure) would have produced a
plausible-looking degraded number with nothing in the artifact to
distinguish it from a clean run. The whole grid was discarded and
re-run rather than salvaged, per this project's own rule: a measurement
from a harness carrying a known defect is invalid and gets redone, not
patched after the fact -- and machine contention during a benchmark run
is exactly such a defect.

Fix: benchmarks/lib/write_manifest.py::machine_load_snapshot() records
load average (1/5/15 min, os.getloadavg()), cpu_count, concurrent
pytest process count, and concurrent Docker container count -- wired
into build_manifest() as `machine_load`, placed alongside `git_sha` in
every MANIFEST.json this harness writes. Best-effort like every other
field in this module (embedding_model_revision, reranker_state): a
failed probe records None rather than aborting manifest generation.

6 new tests (tests_py/benchmarks/test_write_manifest_machine_load.py).
Verified importable and passing with psycopg poisoned out of
sys.modules (matches this module's existing psycopg-independence).

Co-Authored-By: Claude <noreply@anthropic.com>

Follow-up to aa093d2's machine_load_snapshot: that fix captured load only
at the END of a reproduce.sh run (inside write_manifest). A single
end-of-run reading cannot distinguish "this cell ran under contention the
whole time" from "load spiked right at the end" -- exactly the ambiguity
that forced discarding a whole 5-cell sweep rather than salvaging the
cells that merely finished (vs. the one that visibly crashed).

Fix: benchmarks/lib/write_manifest.py::write_start_snapshot() captures the
same machine_load_snapshot() and writes it to RESULTS_DIR/START_SNAPSHOT.json.
benchmarks/reproduce.sh calls it first thing in main(), before start_db, so
it predates even the container/DB overhead. build_manifest() reads that
file back at cell end and folds it into MANIFEST.json as
machine_load_at_start, alongside the renamed machine_load_at_end (was
machine_load). START_SNAPSHOT.json is excluded from the results_files list.

10 tests (was 6), covering both snapshot points and the results_files
exclusion. ruff clean, bash -n clean on reproduce.sh, verified end-to-end
against a throwaway results dir.

Co-Authored-By: Claude <noreply@anthropic.com>

…(CI)

Test (SQLite backend) failed on GitHub's Linux CI runner:
TestMachineLoadSnapshot::test_pytest_process_count_sees_the_process_running_this_test
-- assert 0 >= 1. Not a flaky test: machine_load_snapshot()'s own pytest
process was genuinely undercounted.

Root cause: GNU procps `ps aux` truncates the COMMAND column to $COLUMNS
(default 80) when stdout is not a terminal and COLUMNS is unset -- unlike
BSD ps (macOS), which does not truncate piped output by default, so this
never reproduced locally. `ps aux`'s fixed-width USER/PID/%CPU/... prefix
alone is close to 80 columns, and pytest's actual invocation path
(interpreter + script, e.g. ".../bin/python3.12 .../bin/pytest ...") pushes
the "pytest" substring well past that -- so it was silently cut off on
every Linux CI run, not just this one. A real undercount in the manifest
field this whole fix exists to make trustworthy, not merely a test bug.

Fix: pass an explicit wide `COLUMNS` override in the `ps aux` subprocess
environment -- both GNU procps and BSD ps honor it, so this is portable
and harmless where it wasn't the problem (macOS).

Co-Authored-By: Claude <noreply@anthropic.com>